Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1182

reference: 227-tree-1
name: 1182
tree-preservation-order: undefined
227-tpo-1
uprn
address-text
point: POINT (-1.028542 50.866526)
geometry: MULTIPOLYGON (((-1.028514 50.866523,-1.028515 50.866529,-1.028519 50.866534,-1.028533 50.866541,-1.028542 50.866542,-1.028551 50.866541,-1.028559 50.866538,-1.028565 50.866534,-1.028571 50.866524,-1.028566 50.866513,-1.028551 50.866506,-1.028534 50.866506,-1.028526 50.866509,-1.028515 50.866518,-1.028514 50.866523)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL